
Sentient Blade
Walk It Off
531
|
Posted - 2012.11.30 12:56:00 -
[1] - Quote
Nice changes.
The only thing I would point out is that the loss of corporate hangers is going to be somewhat of a pain. On the Orca yes, but even more so on capital ships where the size of the hanger is limited + cans are in short supply, it's going to make separating items up a bigger pain.
The best "technical" solution I could come up with would be selectable elastic containers:
Quote:* Buy an "Elastic Shipping Container" for something like 10m ISK (affordable for those flying orcas / capitals) that has an packaged size of say 100 m3.
* You assemble it, and it turns it into an "ElasticContainerer100" with an initial volume of 100 m3.
* You fill it with items you wish to separate, a particular kind of module lets say, but need a bit more room.
* You click on it, select "resize to ..." and select a bigger size, let's say you want to store a couple of frigates along side the modules, so you select 10,000 m3.
* The servers check the size of the parent container to see if the new 10,000 m3 would fit, minus the existing container, and if it does you flip the TypeID to a new "ElasticContainer10000" type, copy / replace it if necessary, and move all the items over.
* Shrink them back down after their job is done provided their content is not oversized.
This would:
Quote:* Allow fleet hangers to have password protected cargo areas that could share space
* Not have to deal with the problems associated with shrink wrap; just spam TypeIDs for non-market containers and swap between them.
* Allow Orca / Carrier pilots to keep a few of these elastic containers always to hand to be use to partition their ships where necessary without having to haul empty cans just in case for no reason other than the code that handled a cargo bay having "dividing walls" needed to die (understandable).
Caveats:
Quote:* You do not need to spam hidden containers for every 100 m3 for the entire range, 25, 100, 250, 500, 1000, 2000, 3000, 4000, 5000, 7500, 10000, 15000, 20,000 etc.
* Removing the existing container from the DB and creating a new one with the same children and attributes (except TypeID) would be perfectly acceptable. If this means people have to re-open the can so be it.
* Repackaging them would return them back to a particular size "Elastic Shipping Container" which could then be sold on the market.
So CCP, a better idea than just removing them completely, no? |